<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-gb" lang="en-gb" dir="ltr" >
<!--
- CopyRight:  (C) dGB Earth Sciences
- Author:     A.H. Bril
- Date:       June 2008
- Contents:   FlexNet usage and installation
- RCS:        $Id$
-->

  <head>
  <meta http-equiv="content-type" content="text/html; charset=utf-8" />
  <title>FlexNet installation and usage</title>
  <link rel="stylesheet" href="style.css" type="text/css" />
  </head>
<body id="page_bg" class="width_fmax">
<a name="top"></a>

<div id="all">
        <div id="wrapper">
                <div id="wrapper_r">
<div id="header">
                                <div id="header_l">
                               
                                        <div id="header_r">
                                                <div id="topbanner"></div>
                                                <div id="topmenu">
                                                </div>
                        <div id="leftcolumn">  
<table id="greenborder"><tbody>
<tr><td valign="top">

<center>
| <a href="#intro">Introduction</a>
| <a href="#install">Installation</a>
| <a href="#expert">Experts</a>
</center>
<h2><a name="intro">Introduction</a></h2>
  <p>On Windows, installation of the license file is quite a bit more difficult than on UNIX variants. Especially if you also have to startup a license manager daemon (i.e. if you have a server-based license) as a Windows service. We therefore recommend, if you have the chance, to use a UNIX server for licensing if you have the chance.</p>
  <p>How do you know whether you have a server-based license? Well, you need to look inside the file, with a tool like the Notepad. If you see a line like:</p>
<pre>SERVER the_host 00828d72b0</pre>
<p>then you know you have a floating license. Setting up the license will be harder, but you will be more flexible in the computers you use. See also the <a href="http://opendtect.org/lic/doc/flexnet_explained.html">FlexNet Explained</a> page.
</p>

<h2><a name="install">Installation</a></h2>
<p>
The installation starts by putting the license file in a good, stable, safe position on your system. This is <b>not</b> in the installation directory (which is typically \Program Files\OpendTect). A directory like \Licenses and a filename showing the plugin vendor name seems to be a good choice. We recommend not to use spaces or special characters in the directory or file name. Later, when you get a new license file, you simply replace the old one with the new one under the same name. If the license is floating use the 'ReRead License File' button in the 'Start/Stop/ReRead' tab of the license manager tools program.
</p>
  <p>If you are upgrading, i.e. replacing a license file with a new version, then the easiest way to do it is to replace only the contents of the old file, i.e. keeping the same name. For server-based licenses, first stop the service. In any case, don't keep old copies in existence because FlexNet may sneakily use those rather than trying the new one.</p>
<p>
  For new installations: on first usage of a plugin, you will see a popup of a window asking for the license file. If this method succeeds, everything should be OK. You can stop reading now.<br />
</p><p>
  Unfortunately, in many cases you have to set up the license in a different way. For this, you need to use the 'License Manager Tools' program, which can be started from the Windows start menu for OpendTect.<br /><br />
  <img src="pics/win_startmenu.png" alt="win_startmenu" /><br /><br />
</p><p>
The first thing you need to be sure of, is that FlexNet is looking at the right file for the right license feature. For this, go to the Utilities tab and check by using the 'List all vendor paths' button whether there is a path to your license file - for the vendor in question. For example, for dGB, the vendor name is 'dgbld', for ArkCls, it's 'arkclsld'. You can find your vendor's name in the license file.
</p><p>
  In case you see a wrong path displayed, you can overrule it using the overrule button. Below an example for the dGB daemon ('dgbld'), for other vendors you need to use other names (e.g. 'arkclsld'):<br />

  <i>Please note the vendor names for license files: <b>dGB = dgbld</b>; <b>ArkCLS = arkclsld</b>; <b>Sitfal = geoinfo</b></i><br /><br />

  <img src="pics/override_path.png" alt="override_path" /><br /><br />
</p><p>
If you have a node-locked or demo license, you should now be able to use the plugins.
  </p><p>For licenses requiring a server, you must also make sure the FlexNet vendor service is running on the server machine. On the server machine, start the License Manager Tools program. In the top tab select 'Configuration using services'. Go to the 'Config services' tab. Now enter a name for the service, for example 'opendtect_lic' in the 'Service name' field. The location of the lmgrd.exe file may differ per vendor. They are in the installation, under Program Files\OpendTect\4.4.0. Then find the necessary lmgrd.exe in:</p>
<ul>
  <li><i>dGB</i>: bin\win32\lm.dgb</li>
  <li><i>ARK CLS</i>: arkcls\bin\Windows\5.1\i686</li>
  <li><i>SITFAL</i>: SITFAL\bin\win32\lm.sitfal</li>
</ul>
  <p>The debug log file is traditionally given the license file's name with extension '.log'. Below example is for dGB (for ARK CLS you'd need to use something like arkcls\bin\Windows\5.1\i686\lmgrd.exe):<br /><br />
    <img src="pics/config_services.png" alt="config_services" /><br /><br />
Press 'Save service' and go to the Start/Stop/Reread tab. After starting the server, the licenses are ready to use.
</p><p>
  If for some reason the license fails to be granted, you should examine:</p>
<ul>
  <li>The OpendTect console messages</li>
  <li>The debug log file (when you started a service)</li>
  <li>The plugin management window (Utilities-plugins)</li>
</ul><p>
You can also take a look at the <a href="#expert">expert approach</a>.
</p>
<p>If you are using the Windows firewall, the following may be necessary (reported by Curtis A. Link from MontanaTech). In the Windows Firewall interface (Control Panel), under the Exceptions tab, use Add Program and Browse to point to lmgrd.exe and click Open. Next do the same thing for the vendor daemon dgbld.exe. Finally, a reboot (this was key).</p>

<h2><a name="expert">Expert approach</a></h2>
More advanced ways of managing license files, services and so forth are
possible. Two approaches were described by power-users:

<ol>
<li>
  <b>David Epelboim</b> of <a href="http://www.geoinfo.com.ar">GeoInfo Argentina</a> describes <a href="flexnet_inst_win_expert.html#david">a full procedure of installing on Windows</a>.</li>

<li>
  <b>Julien Moreau</b> of the <a href="http://www.seismo.helsinki.fi">University of Helsinki</a> describes <a href="flexnet_inst_win_expert.html#julien">a way to run multipe license managers under one service</a>.</li>
</ol>

</td></tr></tbody></table>
</div>
                         <div id="footer">
                         </div>
                         </div>
                 </div>
         </div>
 </div>
</div>
</div>

</body>
</html>

